Salesforce Environments
When changes to Salesforce or one of the connected sites are requested, we follow a structured process: we create a private development instance, move to a Quality Assurance (QA) instance for internal review, then to a User Acceptance Testing (UAT) instance for your approval. Only after everything is verified, changes are deployed to our production instance.
For testing purposes, you may be required to log into one of our listed UAT or Test instances to ensure your project meets your requirements.
Development Sandboxes
Each developer can have their own scratch and dev sandboxes - as many as are needed.
In addition to these individual developer sandboxes, we have a shared testing environment.
Where you work: https://aanp--uat02.sandbox.my.salesforce.com
Where members connect: https://home.aanpqa.com
Items to note
How it's used - AANP Dev projects being developed will be configured and tested here. Once reviewed, the changes will ultimately be merged into the User Acceptance Testing (UAT) instance where I2C's updates will also be included.
Two Teams, One Product - The internal development team is working with I2C, and external consulting group, to build our Salesforce instance.
Testing Help - If you are working with the Dev Team, we may ask you to login to this site to test and provide feedback
Login Info May Differ - You may need separate credentials with a new username and password for the testing site. Work with the Dev Team to get setup, and keep those credentials handy!
Consultants and dev team members may show you work they are doing in these sandboxes, but it won't be exactly like our production instances and will have little to no production data.
Staging
Where you work: https://aanp--staging.sandbox.my.salesforce.com
Where users connect: https://home.aanpuat.com
Items to note
How it's used - If you are working with the Dev Team, we may ask you to login to these sites to test and provide feedback
Full Sandbox - This is a full copy of our production environment, and we can copy over ALL data from production. We can also ADD as much data as we want into this sandbox as well. Previously we were severely limited in the number of records we could test.
Login Info May Differ - You may need separate credentials with a new username and password for the testing site. Work with the Dev Team to get setup, and keep those credentials handy!
Production Environments
Where you work: https://aanp.my.salesforce.com
Where members connect: https://home.aanp.org
Items to note
How it's used - this is the final stop for Salesforce development, our live, user facing system. This is where you will work, day to day.
Impersonate - You are able to impersonate any member or non-member that has created an account on our site, without knowing their password.
No Password Access - You will no longer be able to view a user's password. You can send them a password reset to their email address instead.
Marketing Cloud
Where you work: https://mc.s13.exacttarget.com/
Items to note
How it's used - Marketing Cloud is where most of our emails are processed and delivered to users.
Replacement for Existing Products: You may have heard the terms “Real Magnet” and “SendGrid” used at AANP when discussing email delivery. Marketing Cloud will replace the use of those to deliver both Transactional and Marketing emails over time. PropFuel, however, will stick around.
Limited Userbase - Initially, we think Dev Team, Marketing and Membership will have access to this account. However, as we explore, we may provide more access with limited privileges to others.
User 360 - Salesforce and Marketing Cloud are tightly integrated. You will see statistics and information about email delivery inside Salesforce without having to login to Marketing Cloud directly, including if an email was delivered AND if they opened it!